|
'Enable Caller ID'
configure voip > gateway dtmf-supp-service supp-service-settings > enable-caller-id
[EnableCallerID]
|
Global parameter that enables Caller ID.
|
✔
|
FXS: The calling number and display text (from IP) are sent to the device's port.
|
To configure the Caller ID string per port, see Configuring Caller Display Information. To enable or disable caller ID generation / detection per port, see Configuring Caller ID Permissions.
|
|
'Caller ID Type'
configure voip > gateway dtmf-supp-service supp-service-settings > caller-id-type
[CallerIDType]
|
Determines the standard used for generation (FXS) of Caller ID, and generation (FXS) of MWI (when specified) signals:
|
■
|
[0] Standard Bellcore = (Default) Caller ID and MWI
|
|
■
|
[1] Standard ETSI = Caller ID and MWI
|
|
■
|
[4] Standard BT = Britain
|
|
■
|
[16] Standard DTMF Based ETSI |
|
■
|
[17] Standard Denmark = Caller ID and MWI
|
Note:
|
■
|
The parameter is applicable only to analog interfaces.
|
|
■
|
Typically, the Caller ID signals are generated / detected between the first and second rings. However, sometimes the Caller ID is detected before the first ring signal. In such a scenario, set the [RingsBeforeCallerID] parameter to 0.
|
|
■
|
To select the Bellcore Caller ID sub standard, use the [BellcoreCallerIDTypeOneSubStandard] parameter. To select the ETSI Caller ID substandard, use the [ETSICallerIDTypeOneSubStandard] parameter.
|
|
■
|
To select the Bellcore MWI sub standard, use the [BellcoreVMWITypeOneStandard] parameter. To select the ETSI MWI sub standard, use the [ETSIVMWITypeOneStandard] parameter.
|
|
■
|
If you define Caller ID Type as NTT [2], you need to define the NTT DID signaling form (FSK or DTMF) using the [NTTDIDSignallingForm] parameter.
|
|
|
'Enable FXS Caller ID Category Digit For Brazil Telecom'
fxs-callid-cat-brazil
[AddCPCPrefix2BrazilCallerID]
|
Enables the interworking of Calling Party Category (cpc) code from SIP INVITE messages to FXS Caller ID first digit.
When the parameter is enabled, the device sends the Caller ID number (calling number) with the cpc code (received in the SIP INVITE message) to the device's FXS port. The cpc code is added as a prefix to the caller ID (after IP-to-Tel calling number manipulation). For example, assuming that the incoming INVITE contains the following From (or P-Asserted-Id) header:
From:<sip:+551137077801;cpc=payphone@10.20.7.35>;tag=53700
The calling number manipulation removes "+55" (leaving 10 digits), and then adds the prefix 7, the cpc code for payphone user. Therefore, the Caller ID number that is sent to the FXS port, in this example is 71137077801.
If the incoming INVITE message doesn't contain the 'cpc' parameter, nothing is added to the Caller ID number.
|
CPC Value in Received INVITE
|
CPC Code Prefixed to Caller ID (Sent to FXS Endpoint)
|
Description
|
|
cpc=unknown
|
1
|
Unknown user
|
|
cpc=subscribe
|
1
|
-
|
|
cpc=ordinary
|
1
|
Ordinary user
|
|
cpc=priority
|
2
|
Pre-paid user
|
|
cpc=test
|
3
|
Test user
|
|
cpc=operator
|
5
|
Operator
|
|
cpc=data
|
6
|
Data call
|
|
cpc=payphone
|
7
|
Payphone user
|
Note:
|
■
|
The parameter is applicable only to FXS interfaces.
|
|
■
|
For the parameter to be enabled, you must also set the parameter EnableCallingPartyCategory to 1.
|
|
|
[EnableCallerIDTypeTwo]
|
Disables the generation of Caller ID type 2 when the phone is off-hooked. Caller ID type 2 (also known as off-hook Caller ID) is sent to a currently busy telephone to display the caller ID of the waiting call.
|
■
|
[0] = Caller ID type 2 isn't played.
|
|
■
|
[1] = (Default) Caller ID type 2 is played.
|
Note: The parameter is applicable only to FXS interfaces.
|
|
configure voip > interface fxs-fxo > caller-id-timing-mode
[AnalogCallerIDTimingMode]
|
Determines when Caller ID is generated.
|
■
|
[0] = (Default) Caller ID is generated between the first two rings.
|
|
■
|
[1] = The device attempts to find an optimized timing to generate the Caller ID according to the selected Caller ID type.
|
Note:
|
■
|
The parameter is applicable only to FXS interfaces.
|
|
■
|
If the parameter is set to 1 and used with distinctive ringing, the Caller ID signal doesn't change the distinctive ringing timing.
|
|
■
|
For the parameter to take effect, a device restart is required.
|
|
|
configure voip > interface fxs-fxo > bellcore-callerid-type-one-sub-standard
[BellcoreCallerIDTypeOneSubStandard]
|
Determines the Bellcore Caller ID sub-standard.
|
■
|
[0] = (Default) Between rings.
|
|
■
|
[1] = Not ring related.
|
Note:
|
■
|
For the parameter to take effect, a device restart is required.
|
|
■
|
The parameter is applicable only to FXS interfaces.
|
|
|
configure voip > interface fxs-fxo > etsi-callerid-type-one-sub-standard
[ETSICallerIDTypeOneSubStandard]
|
Determines the ETSI FSK Caller ID Type 1 sub-standard (FXS only).
|
■
|
[0] = (Default) ETSI between rings.
|
|
■
|
[1] = ETSI before ring DT_AS.
|
|
■
|
[2] = ETSI before ring RP_AS.
|
|
■
|
[3] = ETSI before ring LR_DT_AS.
|
|
■
|
[4] = ETSI not ring related DT_AS.
|
|
■
|
[5] = ETSI not ring related RP_AS.
|
|
■
|
[6] = ETSI not ring related LR_DT_AS.
|
Note:
|
■
|
For the parameter to take effect, a device restart is required.
|
|
■
|
The parameter is applicable only to FXS interfaces.
|
|
|
'Asserted Identity Mode'
asserted-identity-m
[AssertedIdMode]
|
Determines whether the SIP header P-Asserted-Identity or P-Preferred-Identity is added to the sent INVITE, 200 OK, or UPDATE request for Caller ID (or privacy). These headers are used to present the calling party's Caller ID, which is composed of a Calling Number and a Calling Name (optional).
|
■
|
[0] Disabled = (Default) P-Asserted-Identity and P-Preferred-Identity headers are not added. |
|
■
|
[1] Add P-Asserted-Identity |
|
■
|
[2] Add P-Preferred-Identity |
The used header also depends on the calling Privacy (allowed or restricted). These headers are used together with the Privacy header. If Caller ID is restricted (i.e., P-Asserted-Identity is not sent), the Privacy header includes the value 'id' ('Privacy: id'). Otherwise, for allowed Caller ID, 'Privacy: none' is used. If Caller ID is restricted (received from Tel or for analog interfaces, configured on the device), the From header is set to <anonymous@anonymous.invalid>.
|